-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EDR Workflows] Workflow Insights - migrate to Signature field #205323
base: main
Are you sure you want to change the base?
[EDR Workflows] Workflow Insights - migrate to Signature field #205323
Conversation
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a question, but approving anyway 👍
@@ -122,7 +122,9 @@ export const WorkflowInsightsResults = ({ | |||
{insight.message} | |||
</EuiText> | |||
<EuiText size={'xs'} color={'subdued'}> | |||
{item.entries[0].type === 'match' && item.entries[0].value} | |||
{item.entries[0].type === 'match' && |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to make sure: we add more checks, so all of them have to be met in order to be valid?
This PR adds checks to verify whether the signer_id is present in file events stored in the ES, which serve as the foundation for generating endpoint insights. Previously, we relied solely on the executable path, which caused issues when a single AV generated multiple paths.
With these changes:
signer_id
exists in the file event, it will be used for generating insights.signer_id
is unavailable (e.g., Linux, which lacks signers), the executable path will still be used as a fallback.Screen.Recording.2024-12-31.at.15.31.24.mov